Intel® DMI to SNMP Mapper Version 1.1 for Microsoft Win32* Release Notes

This document contains information about the above product in these sections:

1. Release Contents
2. Target Environments
3. Technical Support Information
4. Pre-installation Requirements
5. Installation Instructions
6. Operating Instructions
7. Product Release Notes

1. Installation program, setup.exe
   
   
2. Product release note
   
   
3. License agreement
   
   
4. Intel DMI to SNMP Mapper files list:
   
   
   • Management Information Base (MIB) Generator:
     • MIBGEN.EXE
     • MIBGEN.CFG
     
     
   • Win32 DMI to SNMP run-time agent:
     • DMI2SNMP.DLL
     
     
   • Microsoft Files
     • SNMPAPI.DLL
     • MSVCRT.DLL
     • MFC42.DLL
     
     
   • Documentation
     • DMI2SNMP.DOC (User Guide)
     
     
   • Standard MIBs
     This includes DMTF-DMI.MIB and these Desktop Management Task Force, Inc. (DMTF) standard MIBs:
     • dmtf-systems.mib
     • dmtf-mobile.mib
     • dmtf-lanadapter.mib
     • dmtf-software.mib
     • dmtf-slayer.mib
     • dmtf-monitor.mib

1. Microsoft SNMP Master Agent (any version) must be installed on target machine.
   
   
2. Intel DMI 2.0 Service Provider (SP) Software Development Kit (SDK) (release 2.32 or later) must be installed on the target machine.

The setup.exe can be used in "silent mode installation". In conjunction with a response file, the silent mode allows you to install the Intel DMI to SNMP Mapper without any user interaction. A default response file, setup.iss, is provided with this installation package. To run the default silent install, use the following command line:

setup -s -fsetup.ins -f1setup.iss /SMS

Uninstall procedure for Intel DMI to SNMP Mapper

To uninstall the Intel DMI to SNMP Mapper, click the Uninstall icon in the Intel DMI 2.0 to SNMP Mapper program folder or use the Add/Remove Programs icon located in the Control Panel.

5.1) Manual installation instructions
--------------------------------------------------

1. Create the directory C:\Program Files\Intel\DMI 2.0 to SNMP Mapper\BIN.
   
   
2. Copy MIBGEN.EXE and DMI2SNMP.DLL to C:\Program Files\Intel\DMI 2.0 to SNMP Mapper\BIN.
   
   
3. Create this registry key (using regedt32.exe): SOFTWARE\Intel\DMI 2.0 to SNMP Mapper\CurrentVersion.
   
   
4. Create this registry string name: SOFTWARE\Intel\DMI 2.0 to SNMP Mapper\CurrentVersion\Pathname.
   Set its value to C:\Program Files\Intel\DMI 2.0 to SNMP Mapper\BIN\DMI2SNMP.DLL.
   
   
5. Set the value of the DMI2SNMP string name in the SYSTEM\CurrentControlSet\Services\SNMP\Parameters\ExtensionAgents registry key to SOFTWARE\Intel\DMI 2.0 to SNMP Mapper\CurrentVersion.
   
   
6. Copy the following standard Microsoft DLLs to system directory with version control: SNMPAPI.DLL (ver.3.51.1057.5 or later), MSVCRT.DLL(ver.4.20.0.6164 or later), MFC42.DLL(ver.4.2.0.6068 or later).

• The DMI to SNMP Mapper does not act as a Remote Proxy.
  
  
• The DMI to SNMP Mapper does not support the RowStatus OBJECT, necessary for DmiAddRow and DmiDeleteRow mapping.
  
  
• This version of the DMI to SNMP MIB Generator uses the naming convention a bit differently than the proposed standard specification. The mapping schema is fully compliant with the proposed standard specification, however.
  
  
• This version of the DMI to SNMP Mapper (both the MIB generator and the SNMP Agent Extension) does not support multi-language and Unicode mapping. DMI components that do not support a default language (en|US|iso8859-1) are skipped by the DMI to SNMP Mapper.
  
  
• Hewlett-Packard's OpenView* (HP OV) Network Node Manager (NNM) Release 5.0x cannot load MIB files with Object IDs (OIDs) larger than 2147483647. This known issue is corrected in consolidated path NNM_00046.EXE released by Hewlett-Packard. Install the patch, which can be downloaded from http://ovweb.external.hp.com/cpe/patches/index.html, on the HP OV NNM console.
  
  
• For the DMI to SNMP Mapper to function properly, the DMI Service Provider must be running. If the SNMP Master Agent starts prior to the DMI Service Provider, then the DMI to SNMP Mapper returns SNMP_ERRORSTATUS_NOSUCHNAME for every request to DMTF-MIB. The DMI to SNMP Mapper functions normally within 10 seconds after the DMI Service Provider is started and initialized. If the DMI Service Provider is stopped and restarted while the SNMP Master Agent is running, the DMI to SNMP Mapper will return an error for the first SNMP request, and then will function normally.
  
  
• The current implementation of DMI to SNMP Mapper handles SNMP pragma OIDs only under 1.3.6.1.4.1 (enterprises). If the SNMP pragma OID is out of the 1.3.6.1.4.1 scope, the Mapper ignores it and generates a dynamic OID.
  
  
• After the start of the SNMP Master Agent, if a new DMI class is installed outside of the dmtf sub-tree [1.3.6.1.4.1.412] (but within the enterprises sub-tree [1.3.6.1.4.1]), this class will not be accessible through the DMI to SNMP Mapper. To make it accessible, the SNMP Master Agent must be restarted. This occurs because the SNMP Master Agent allows the user to specify the MIB sub-trees that the extension agent supports only when it is started.
  
  
• The run-time agent guarantees the lexicographic order for an SNMP getnext request for the first part of an OID, including DMI component ID and group ID. It does not guarantee it for the keys' part of an OID inside of a specific DMI component and group.
  
  
• The "DMTF DMI to SNMP Standard" for DMTF-DMI.MIB defines DmiInteger64 ::= OCTET STRING (SIZE(8)) and DmiDate ::= OCTET STRING (SIZE (25)). The earlier version of MIFTOMIB.EXE v1.0a generates MIB files with DmiInteger64 ::= INTEGER and DmiDate ::= OCTET STRING (SIZE (28)).
  
  If this type of MIB is loaded on an HP NNM console, this may lead to an error during loading of the DMTF-DMI.MIB in HP NNM console. In order to prevent this conflict, DmiInteger64 is renamed to Dmi_Integer64 and DmiDate is renamed to Dmi_Date, in DMITD-DMI.MIB, DMTF standard MIBs and all MIBs generated by MIBGEN.EXE.